Skip to main content

Your data has issues

There is a problem

  • geometry column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Organisation Felled date Entry date Start date End date
851 Mar-82 ELM PARK ROAD

Unexpected geom type

2025-01-03
852 Jul-89 ELM PARK ROAD

Unexpected geom type

2025-01-03
853 Jul-92 ELM PARK ROAD

Unexpected geom type

2025-01-03
854 13/92 ELM PARK ROAD

Unexpected geom type

2025-01-03
855 Feb-93 ELM PARK ROAD

Unexpected geom type

2025-01-03
856 30/96 ELM PLACE

Unexpected geom type

2025-01-03
857 K71 ELM PLACE

Unexpected geom type

2025-01-03
858 K71 ELM PLACE

Unexpected geom type

2025-01-03
859 K71 ELM PLACE

Unexpected geom type

2025-01-03
860 Nov-73 ELM PLACE

Unexpected geom type

2025-01-03
861 Nov-73 ELM PLACE

Unexpected geom type

2025-01-03
862 Nov-73 ELM PLACE

Unexpected geom type

2025-01-03
863 Nov-73 ELM PLACE

Unexpected geom type

2025-01-03
864 Nov-73 ELM PLACE

Unexpected geom type

2025-01-03
865 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
866 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
867 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
868 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
869 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
870 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
871 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
872 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
873 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
874 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
875 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
876 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
877 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
878 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
879 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
880 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
881 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
882 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
883 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
884 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
885 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
886 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
887 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
888 K6 ELSHAM ROAD

Unexpected geom type

2025-01-03
889 Dec-75 ELSHAM ROAD

Unexpected geom type

2025-01-03
890 16/78 ELSHAM ROAD

Unexpected geom type

2025-01-03
891 Mar-92 ELSHAM ROAD

Unexpected geom type

2025-01-03
892 44/95 ELSHAM ROAD

Unexpected geom type

2025-01-03
893 Jul-74 EMBANKMENT GARDENS

Unexpected geom type

2025-01-03
894 Jun-78 EMPEROR'S GATE

Unexpected geom type

2025-01-03
895 Jan-86 EMPEROR'S GATE

Unexpected geom type

2025-01-03
896 Jul-72 ESSEX VILLAS

Unexpected geom type

2025-01-03
897 Jul-72 ESSEX VILLAS

Unexpected geom type

2025-01-03
898 Jul-72 ESSEX VILLAS

Unexpected geom type

2025-01-03
899 Jul-72 ESSEX VILLAS

Unexpected geom type

2025-01-03
900 K47 EVELYN GARDENS

Unexpected geom type

2025-01-03

Showing rows 851 to 900 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL